home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98a.txt
/
000049_icon-group-sender _Tue Feb 24 08:22:29 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.7/8.8.7) with SMTP id IAA07075
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Tue, 24 Feb 1998 08:22:21 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA21060; Tue, 24 Feb 1998 08:22:19 -0700
Date: Wed, 18 Feb 1998 14:52:39 -0600
Message-Id: <199802182052.OAA30557@segfault.cs.utsa.edu>
From: Clinton Jeffery <jeffery@segfault.cs.utsa.edu>
To: evans@gte.net
Cc: icon-group@optima.CS.Arizona.EDU
In-Reply-To: <34EB3A18.20BF@gte.net> (message from Mark Evans on Wed, 18 Feb
1998 13:44:24 -0600)
Subject: Re: Stand-alone executables
Reply-To: jeffery@cs.utsa.edu
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 485
Mark,
Brute force in this case means literally that I create a .exe file by
concatenating the icode file onto the end of the wiconx.exe (or nticonx.exe).
This is the opposite of: going through standard .exe format conventions to
insert the icode as extra data in the .exe file, which is the job of a
linker or resource compiler.
I am not sure this thread is interesting to everyone in Icon group, so if
have any more technical questions, I'll discuss it with you privately.
Clint